Problem Note 65345: A deadlock occurs in SAS® Workflow Services when you attempt to transition a business object from one workflow state to another
 |  |  |  |  |
In a SAS® solution such as SAS® Model Risk Management or SAS® Enterprise GRC, you might not be able to transition a business object from one workflow state to another. When you edit a business object and click a button to move the object to the next workflow activity, the workflow state might not change.
The issue can be caused by a deadlock when you use IBM DB2 for your SAS® Shared Services database. When this type of deadlock occurs, the SASWorkflowServices9.4 log file contains an error similar to the following:
org.springframework.dao.DeadlockLoserDataAccessException
### Error querying database. Cause: com.ibm.db2.jcc.am.SqlTransactionRollbackException: DB2 SQL Error: SQLCODE=-911, SQLSTATE=40001, SQLERRMC=2, DRIVER=3.66.46
...
### The error may involve Process.selectByWorkflowObjectIdForUpdate-Inline
Click the Hot Fix tab in this note to access the hot fix for this issue.
With this fix, SAS Workflow Services retries the failing policy after a deadlock occurs during policy execution. The retry occurs regardless of the type of database engine for the SAS Shared Services database.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Web Infrastructure Platform | Solaris for x64 | 9.4_M3 | 9.4_M5 | 9.4 TS1M3 | 9.4 TS1M5 |
| Linux for x64 | 9.4_M3 | 9.4_M5 | 9.4 TS1M3 | 9.4 TS1M5 | ||
| HP-UX IPF | 9.4_M3 | 9.4_M5 | 9.4 TS1M3 | 9.4 TS1M5 | ||
| 64-bit Enabled Solaris | 9.4_M3 | 9.4_M5 | 9.4 TS1M3 | 9.4 TS1M5 | ||
| Microsoft® Windows® for x64 | 9.4_M3 | 9.4_M5 | 9.4 TS1M3 | 9.4 TS1M5 | ||
| 64-bit Enabled AIX | 9.4_M3 | 9.4_M5 | 9.4 TS1M3 | 9.4 TS1M5 | ||